This avoids a warning like this one (on Debian 12, using systemd 231)

# systemd-analyze verify /lib/systemd/system/freeradius.service
/lib/systemd/system/freeradius.service:23: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon.```

Is there any change in behaviour? Or the systemd guys just like renaming things to keep people on their toes?

As well as potential change of behaviour, this also needs checking that it doesn't break any of the older Debian-based distros as they are all built using the same source.

@arr2036: It seems to be related to this info in the v252 release of systemd and them dropping cgroupsv1 at some point as described in the "history" section of systemd.resouce-control(5). Also the NEWS file mentions that they plan on dropping it completely with v258.

Considering that (likely) until 4.x gets released, very old distributions based of Debian or RHEL are likely long gone, but for 3.2 it might be worth to do some more checking.

@mcnewton : For what I can see on Debian 12, it's pretty much a drop-in replacement, but I agree with you, that it needs proper checking. There is one other example I found from a package from Red Hat where they updated it for RHEL 9 in redhat-cloud-client-configuration (RHEL-17009).

How distributions using the InkBridge repositories might be affected

InkBridge Networks builds FreeRADIUS packages for RHEL- and Debian-based distributions from this repository, but "only" for the 3.0 & 3.2 releases, not for master or the upcoming 4.x version so these shouldn't be affected IMO. (BTW: Thank you for this service!)

Debian-based distributions

• The oldest Debian builds are for version 9 / stretch, It shipped with systemd 232 (systemd_232*deb9*.deb).
  No new packages have been built since 2022 for 3.0 and 2023 for 3.2
• The oldest Ubuntu builds are for version 18.04 / bionic, it shipped with systemd 237.
  No new packages have been built since 2022 for 3.0 and 2023 for 3.2

(RH)EL-based distributions

• Rocky 8 is likely not affected, it shipped with systemd 239
• The oldest RHEL-based/-derived distribution is CentOS 7, it shipped with systemd 219.
  New packages have been built in 2025 so this one would be affected by a backport to the 3.2 branch.

Should I update the to only change the behaviour for Debian?

The reasoning is, that since the initial PR things have changed as follows:

• master branch includes the modification for Redhat (with: 87a6842)
• v3.2.x branch includes the modification for both Redhat (with: 87a6842) and Debian (with: b9d57d3) systems